Modifying characteristics of a medical device utilizing a mobile device

ABSTRACT

Methods, computer systems and computer readable media for modifying characteristics of a medical device via a mobile device are provided. In embodiments, data communicated by an infusion device providing an infusion to a patient is provided to a mobile device associated with a clinician. A notification associated with the infusion device is received and communicated to the mobile device. Confirmation of the notification is received from the clinician via the mobile device and the notification is communicated to the infusion device. Characteristics of the infusion are automatically modified in accordance with the notification.

BACKGROUND

Infusion pumps infuse fluids, medications and/or nutrients into thecirculatory system of an individual or patient. The infusions may beintravenous, arterial, epidural and the like. Infusion pumps canadminister injections continuously, intermittently, or upon patientrequest. Infusion pumps are used by clinicians for patients when moreaccuracy is needed than with manually adjusted gravitationaladministration of fluids into a patient's circulatory system. Infusionspumps can be used for infusion of a variety of fluids and medicationsincluding, but not limited to anesthesia, chemotherapy, IV drugs, bloodtransfusions and the like.

In many cases, various characteristics of a medical device, such as aninfusion device, need to be modified. Although an order may be enteredthat includes such modifications, current infusion devices requireanother clinician to be physically present at the device and manuallymake changes on the device to download the modifications to the device.This causes delays in providing the patient the modifications. In othercases, alarms may be provided by the medical devices that createnuisances for patients, family, and clinicians alike. For example, theclinician may be in the same room as the device and already aware of anissue. However, current devices still provide alarms that have to bemanually silenced by the clinician.

SUMMARY

Embodiments of the present invention are generally directed to methods,computer systems and computer readable media for modifyingcharacteristics of a medical device via a mobile device. Datacommunicated by the device is provided to a mobile device. If anotification (e.g., modification to an order, a change to a suggestedprotocol, or an alarm associated with the device) is received, such asfrom an electronic medical record (EMR), a healthcare application, orthe like, it is provided to the mobile device. Upon confirming thenotification via the mobile device, the notification is communicated tothe medical device. Characteristics (e.g., rate of infusion, dosage,bolus, alarm suppression) of the medical device are automaticallymodified in accordance with the notification.

Accordingly, in one aspect, an embodiment of the present invention isdirected to one or more computer storage media storing computer-useableinstructions that, when used by one or more computing devices, cause theone or more computing devices to perform operations. The operationsinclude providing, at a mobile device associated with a clinician, datacommunicated by an infusion device providing an infusion to a patient.The operations also include receiving a notification associated with theinfusion device. The operations further include receiving a confirmationof the notification from the clinician via the mobile device. Theoperations also include communicating the notification to the infusiondevice. The operations further include automatically modifyingcharacteristics of the infusion in accordance with the notification.

In another embodiment, an aspect is directed to a computer-implementedmethod in a clinical computing environment. The method includesproviding, via a first computing process, a notification at a mobiledevice, the notification being associated with an infusion device. Themethod also includes receiving, via a second computing process, aconfirmation of the notification from the clinician, the confirmationbeing communicated to an electronic medical record associated with apatient receiving an infusion from the infusion device. The methodfurther includes communicating, via a third computing process, thenotification from the EMR to the infusion device. The method alsoincludes automatically modifying, via a fourth computing process,characteristics of the infusion in accordance with the notification.Each computing process is performed by one or more computing devices.

A further embodiment is directed to a system comprising: one or moreprocessors; and one or more computer storage media storing instructionsthat, when used by the one or more processors, cause the one or moreprocessors to: provide a notification at a mobile device, thenotification being associated with an infusion device; receive aconfirmation of the notification from the clinician, the confirmationbeing communicated to an electronic medical record (EMR) associated witha patient receiving an infusion from the infusion device; communicatethe notification from the EMR to the infusion device; and automaticallymodify characteristics of the infusion in accordance with thenotification.

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described in detail below with reference to the attacheddrawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing environment suitableto implement embodiments of the present invention;

FIG. 2 is an exemplary system architecture suitable to implementembodiments of the present invention;

FIG. 3 is a flow diagram showing a method for modifying characteristicsof a medical device in accordance with embodiments of the presentinvention; and

FIG. 4 is a flow diagram showing a method for modifying characteristicsof a medical device in accordance with embodiments of the presentinvention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent components of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

As mentioned above, in many cases, various characteristics of a medicaldevice, such as an infusion device, need to be modified. Although anorder may be entered that includes such modifications, current infusiondevices require another clinician to be physically present at the deviceand manually make changes on the device to download the modifications tothe device. This causes delays in providing the patient themodifications. In other cases, alarms may be provided by the medicaldevices that create nuisances for patients, family, and cliniciansalike. For example, the clinician may be in the same room as the deviceand already aware of an issue. However, current devices still providealarms that have to be manually silenced by the clinician.

Embodiments of the present invention are generally directed to methods,computer systems and computer readable media for modifyingcharacteristics of a medical device via a mobile device. Datacommunicated by an infusion device providing an infusion to a patient isprovided to a mobile device associated with a clinician. A notificationassociated with the infusion device is received and communicated to themobile device. A confirmation of the notification is received from theclinician via the mobile device. The notification is communicated to theinfusion device and characteristics of the infusion are automaticallymodified in accordance with the notification.

Referring to the drawings in general, and initially to FIG. 1 inparticular, an exemplary computing system environment, for instance, amedical information computing system, on which embodiments of thepresent invention may be implemented is illustrated and designatedgenerally as reference numeral 100. It will be understood andappreciated by those of ordinary skill in the art that the illustratedmedical information computing system environment 100 is merely anexample of one suitable computing environment and is not intended tosuggest any limitation as to the scope of use or functionality of theinvention. Neither should the medical information computing systemenvironment 100 be interpreted as having any dependency or requirementrelating to any single component or combination of componentsillustrated therein.

The present invention may be operational with numerous other generalpurpose or special purpose computing system environments orconfigurations. Examples of well-known computing systems, environments,and/or configurations that may be suitable for use with the presentinvention include, by way of example only, personal computers, servercomputers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

The present invention may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include, but are notlimited to, routines, programs, objects, components, and data structuresthat perform particular tasks or implement particular abstract datatypes. The present invention may also be practiced in distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules may be located inlocal and/or remote computer storage media including, by way of exampleonly, memory storage devices.

With continued reference to FIG. 1, the exemplary medical informationcomputing system environment 100 includes a general purpose computingdevice in the form of a server 102. Components of the server 102 mayinclude, without limitation, a processing unit, internal system memory,and a suitable system bus for coupling various system components,including database cluster 104, with the server 102. The system bus maybe any of several types of bus structures, including a memory bus ormemory controller, a peripheral bus, and a local bus, using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronic Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus, also known as Mezzanine bus.

The server 102 typically includes, or has access to, a variety ofcomputer readable media, for instance, database cluster 104. Computerreadable media can be any available media that may be accessed by server102, and includes volatile and nonvolatile media, as well as removableand non-removable media. By way of example, and not limitation, computerreadable media may include computer storage media and communicationmedia. Computer storage media may include, without limitation, volatileand nonvolatile media, as well as removable and nonremovable mediaimplemented in any method or technology for storage of information, suchas computer readable instructions, data structures, program modules, orother data. In this regard, computer storage media may include, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVDs) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage, orother magnetic storage device, or any other medium which can be used tostore the desired information and which may be accessed by the server102. Computer storage media does not comprise signals per se.Communication media typically embodies computer readable instructions,data structures, program modules, or other data in a modulated datasignal, such as a carrier wave or other transport mechanism, and mayinclude any information delivery media. As used herein, the term“modulated data signal” refers to a signal that has one or more of itsattributes set or changed in such a manner as to encode information inthe signal. By way of example, and not limitation, communication mediaincludes wired media such as a wired network or direct-wired connection,and wireless media such as acoustic, RF, infrared, and other wirelessmedia. Combinations of any of the above also may be included within thescope of computer readable media.

The computer storage media discussed above and illustrated in FIG. 1,including database cluster 104, provide storage of computer readableinstructions, data structures, program modules, and other data for theserver 102.

The server 102 may operate in a computer network 106 using logicalconnections to one or more remote computers 108. Remote computers 108may be located at a variety of locations in a medical or researchenvironment, for example, but not limited to, clinical laboratories,hospitals and other inpatient settings, veterinary environments,ambulatory settings, medical billing and financial offices, hospitaladministration settings, home health care environments, and clinicians'offices. Clinicians may include, but are not limited to, a treatingphysician or physicians, specialists such as surgeons, radiologists,cardiologists, and oncologists, emergency medical technicians,physicians' assistants, nurse practitioners, nurses, nurses' aides,pharmacists, dieticians, microbiologists, laboratory experts, geneticcounselors, researchers, students, office assistants and the like. Theremote computers 108 may also be physically located in non-traditionalmedical care environments so that the entire health care community maybe capable of integration on the network. The remote computers 108 maybe personal computers, servers, routers, network PCs, peer devices,other common network nodes, or the like, and may include some or all ofthe components described above in relation to the server 102. Thedevices can be personal digital assistants or other like devices.

Exemplary computer networks 106 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the server 102 may include a modem or other means forestablishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin the server 102, in the database cluster 104, or on any of the remotecomputers 108. For example, and not by way of limitation, variousapplication programs may reside on the memory associated with any one ormore of the remote computers 108. It will be appreciated by those ofordinary skill in the art that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers (e.g., server 102 and remote computers 108) may beutilized.

In operation, a user may enter commands and information into the server102 or convey the commands and information to the server 102 via one ormore of the remote computers 108 through input devices, such as akeyboard, a pointing device (commonly referred to as a mouse), atrackball, or a touch pad. Other input devices may include, withoutlimitation, microphones, satellite dishes, scanners, or the like.Commands and information may also be sent directly from a remotehealthcare device to the server 102. In addition to a monitor, theserver 102 and/or remote computers 108 may include other peripheraloutput devices, such as speakers and a printer.

Although many other internal components of the server 102 and the remotecomputers 108 are not shown, those of ordinary skill in the art willappreciate that such components and their interconnection are wellknown. Accordingly, additional details concerning the internalconstruction of the server 102 and the remote computers 108 are notfurther disclosed herein.

Turning now to FIG. 2, a schematic diagram depicts an operatingenvironment, identified generally by reference numeral 200, suitable topractice an embodiment of the present invention. FIG. 2 includes variouscomponents that communicate with one another, including medical device210, infusion pump devices 212 and 214, clinical user devices 226, bus216, device manager 224, healthcare information system 228 and infusionapplication 232. In one embodiment of the present invention, datagenerated by a medical device 210 or an infusion pump device 212, and214 is routed to and managed by device manager 224, as opposed to, eachmedical device 210 and infusion pump device 212 displaying informationon the medical device or infusion pump respectively. For example, data218, 220, and 222 is communicated to bus 216, which might then forwardthe data to device manager 224 to be further processed and routed.Before describing in more detail how these components communicate, eachcomponent will be generally described.

In an embodiment of the present invention, medical device 210 mightinclude cardiac monitors, ventilators, balloon pumps, patient beds,sequential-compression devices, electronic security devices, andvital-sign detecting devices. Medical device 210 may generate variousdata (e.g., measured heart rate) that, as described in more detailbelow, is communicated to other components (e.g., bus 216) of operatingenvironment 200. Moreover, medical device 210 might also receiveinformation from components of operating environment 200.

In another embodiment of the present invention infusion pumps 212 and214 infuse fluids, medications and/or nutrients into the circulatorysystem of an individual or patient. The infusions may be, but are notlimited to, intravenous, arterial, epidural and the like. Infusion pumpscan administer injections continuously, intermittently, or upon patientrequest. Infusion pumps are used by clinicians for patients when moreaccuracy is needed than with manually adjusted gravitationaladministration of fluids into a patient's circulatory system. Infusionspumps can be used for infusion of a variety of fluids and medicationsincluding, but not limited to anesthesia, chemotherapy, IV drugs, bloodtransfusions and the like. The fluid, medication and/or nutrients aretypically contained in an infusion container, such as an infusion bag.It will be appreciate that any type container may be utilized to holdthe infusion fluid, medication and/or nutrients. Infusion pumps 212 and214 generate various data, including, but not limited to, remainingvolume of infusion (e.g., amount remaining in fluid container), rate ofinfusion (e.g., how fast fluid is being infused), alerts (e.g., air inline, maintenance of pump needed, high backpressure, low infusion,occlusion, or pump stopped). This data is communicated to othercomponents (e.g., bus 216) of operating environment 200. Moreover,infusion pumps 212 and 214 might also receive information fromcomponents of operating environment 200.

Healthcare information system 228 includes an integrated system ofhealthcare-related information that is usable by a healthcare facilityto operate and provide patient care. For example, healthcare informationsystem 228 includes an electronic medical record 229 (also referred toherein as “EMR”) and a healthcare applications component 230. EMR 229includes an electronic version of patient records including informationfor the patient, such as medication and infusion orders, tasks, images,examination reports, testing and lab results, medical history, etc.Healthcare applications component 230 includes information that is inputand provided at a patient's point-of-care (e.g., patient bedside) toassist healthcare professionals to provide appropriate care. Anexemplary applications component 230 includes a patient order entrycomponent for entering electronic healthcare orders for a patient. In anembodiment of the present invention, healthcare information system 228receives information from other components, as will be described in moredetail below. Moreover, healthcare information system 228 might alsoprovide information that is communicated to other components ofoperating environment 200.

Clinical user devices 226 include devices that are used within ahealthcare facility to receive, display and send information to a user,such as a clinician. Clinician user devices 226 also facilitate requeststo receive additional information. Exemplary clinical user devices 226include personal communication devices. Personal communication devicesinclude devices that are used by an individual to receive and sendinformation, such as an in-house phone or a mobile device. Accordingly,in an embodiment of the present invention, clinical user devices 226present to users information that is received from other components ofoperating environment 200. Moreover, clinical user devices 226 mightalso receive inputs from a clinician that are communicated to othercomponents of operating environment 200. Clinical user devices 226 alsocommunicate to other components of operating environment 200 requests toreceive additional information. For example, clinical user device 226might communicate information to infusion application 232, HIS 228, EMR229, healthcare application 230, and medical devices 210, 212 and 214.

Infusion application 232 is an electronic application for receivingmedication orders, such as infusion orders, to be filled. An exemplarypharmacy system is Cerner Millennium Pharmnet by Cerner Corporation,Kansas City Mo. Typically orders for medications, fluids and nutrientsto be filled by a pharmacist are displayed in the pharmacy or pharmacyIV room. The pharmacist can use this information to drive the pharmacyworkflow and make sure the necessary medication orders are filled. Inanother embodiment, infusion application 232 may be an automatedpharmacy dispensing system such as Cerner RXStation by CernerCorporation of Kansas City, Mo. The automated pharmacy system may be anapparatus pre-loaded with medication, fluids and/or nutrients that maybe dispensed to fill patient orders.

As previously indicated, and as depicted in FIG. 2, each of medicaldevices 210, infusion pumps 212 and 214, healthcare information system228, device manager 224, clinical user devices 226 and infusionapplication 232 may be in communication with bus 216. Bus 216 generallyprovides a connection framework for these components by creating andmanaging all connections, providing a messaging architecture tofacilitate an exchange of information between the various components ofFIG. 2, and providing general operational and management capabilitiesfor connected devices. In one embodiment, medical device 210, infusionpumps 212 and 214, device manager 224, clinical user devices 226,healthcare information system 228 and infusion application 232communicate with bus 216 as described in U.S. patent application Ser.No. 12/347,475 (U.S. Pat. App. '475), which is incorporated herein byreference. For example, infusion pumps 212 and 214 might include variousdifferent types of infusion pumps that are manufactured by variousdifferent vendors. As such, components of FIG. 2 might communicate withbus 216 via a gateway (e.g., device gateway or internal gateway), anadapter, or by any other means described by U.S. Pat. App. '475. In afurther embodiment, bus 216 includes those capabilities described inU.S. Pat. App. '475. As indicated in U.S. Pat. App. '475, once data isreceived (e.g., data 218, 220, and 222) it can be sorted and routed toother applications.

In an embodiment of the present invention, such applications areincluded in a device manager 224. As such, bus 216 might receiveinformation (e.g., data 218, 220, and 222) and route the data to devicemanager 224. Moreover, bus 216 might receive information from clinicaluser devices 226 and route the information to device manager 224. In afurther embodiment, bus 216 receives information from healthcareinformation system 228 and routes the information to device manager 224.In another embodiment, bus 216 receives information from device manager224 and routes the information to other components. For example, bus 216routes information from clinical user devices 226 to healthcareinformation system 228.

In an embodiment of the present invention, device manager 224communicates with bus 216 and functions to facilitate the management andcontrol of the medical devices 210, 212, 214 based on informationreceived from the various components of operating environment 200 (e.g.,orders modifications, protocols, alarms, etc.) via clinical user devices226. In this way, a clinician is able to use a clinical user device 226to confirm order modifications, protocols, or silence alarms. Forexample, information form a medical device 210 may indicate that acharacteristic (e.g., dosage, rate, etc.) of an infusion should bemodified. A clinician seeing this information may order the necessarymodification, such as via the EMR 229, healthcare application 230, orinfusion application 232. Upon entering the order, instead of anotherclinician having to physically be at one of the medical devices 210,212, 214 to program the device, that clinician may confirm the orderutilizing the clinical user device 226. The device is then programmedwith the appropriate modification and begins treating the patient in amuch more timely fashion.

Device manager 224 includes notification component 234, confirmationcomponent 236, communication component 238, modification component 240,and proximity component 242. While these components are included in theembodiment of FIG. 2, any number of components, either more or less thanthe illustrated components, may be used to accomplish the purposes ofthe present invention. Other components and subcomponents arecontemplated to be within the scope of the present invention.Furthermore, although depicted as residing on one device, such as aserver, it will be appreciated that any number of components and/orsubcomponents may reside on any number of computing devices or servers.

Notification component 234 is generally configured to receivenotifications associated with medical devices 210, 212, 214. In someembodiments, the notification is associated with an infusion device. Thenotifications may include a modification to an order associated with themedical device. For example, a clinician may have received informationfrom one or more of the medical devices 210, 212, 214 indicating aninfusion order for a patient should be modified. Similarly, theclinician may have received information from the EMR 229 indicating theinfusion order should be modified. In either scenario, the clinician mayenter the modification into the EMR 229, a healthcare application 230,or infusion application 232. Once entered, notification component 234receives the modification and communication component, discussed in moredetail below, communicates the notification to the clinician via aclinical user device 226 (e.g., a mobile device).

Confirmation component 236 is generally configured to receiveconfirmation of the notification from the clinician via a clinical userdevice 226. Accordingly, the clinician is able to quickly andefficiently confirm a modification to an order, change the device toincorporate or utilize a suggested protocol, or silence an alarm on thedevice without being physically in the same location as the medicaldevice 210, 212, 214. In this way, the clinician manages and controlsthe medical devices 210, 212, 214 utilizing the clinical user device 226and can do so from any location. In some embodiments, the confirmationis communicated to the EMR associated with the patient receiving aninfusion from an infusion device.

Communication component 238 is generally configured to communicate thenotification to the medical device. This enables the confirmationreceived from the clinical user device 226 via the confirmationcomponent 236 to cause the medical device to program down thenotification. In this way, the medical device receives the modificationto the order or suggested protocol from the EMR 229, healthcareapplication 230, or infusion application 232, in various embodiments.

Modification component 240 is generally configured to alter thefunctioning of the medical device in accordance with the notification.For example, characteristics of an infusion are automatically modifiedin accordance with the notification. As such, a clinician, by confirminga notification via the clinical user device 226, can control thefunctionality of the medical devices 210, 212, 214. In some embodiments,an infusion is automatically modified in accordance with thenotification.

In embodiments, proximity component 242 is generally configured todetect that the clinical user device 226 is in proximity to the medicaldevice (e.g., infusion device). For example, the proximity component 242may detect that the clinical user device 226 is located in the same roomor physical location as the infusion device. If the infusion device isgenerating some type of alarm that might nuisance a sleeping patient ora clinician that is already aware of an issue causing the alarm becausethe clinician is physically near the infusion device, there is no needto generate an audible alarm. Because proximity component 242 detectsthe presence of the clinician user device, proximity component 242automatically suppresses the alarm associated with the infusion device.Although the alarm is suppressed, data associated with the alarm maystill be communicated by proximity component 242 to the EMR associatedwith the patient.

Turning now to FIG. 3, a flow diagram is provided that illustrates amethod 300 for modifying characteristics of a medical device, inaccordance with embodiments of the present invention. At step 310, datacommunicated by an infusion device providing an infusion to a patient isprovided to a mobile device associated with a clinician. The data mayinclude any data displayed on a display of the infusion device itself.At step 312, a notification associated with the infusion device isreceived. In some embodiments, the notification may include amodification to an order associated with the infusion device. In someembodiments, the notification may be a suggested protocol. In variousembodiments, the notification is communicated from the EMR associatedwith the patient, a healthcare application, an infusion application, andthe like.

The notification is communicated to the mobile device, at step 314. Aclinician may confirm the notification utilizing the mobile device. Aconfirmation of the notification is received, at step 316, from theclinician via the mobile device. The notification is then communicatedto the infusion device, at step 318. As described above, thenotification may be communicated from the EMR associated with thepatient, a healthcare application, an infusion application, and thelike. In this way, the clinician is able to control the infusion deviceutilizing the mobile device. Once the notification is communicated tothe infusion device, characteristics of the infusion device areautomatically modified, at step 320, in accordance with thenotification.

In some embodiments, the notification is an alarm associated with theinfusion device. In one embodiment, it is detected that the mobiledevice is in proximity to the infusion device. The alarm associated withthe infusion device may be automatically suppressed. Data associatedwith the alarm is communicated to the EMR associated with the patient.

With reference now to FIG. 4 a flow diagram is provided that illustratesa method 400 modifying characteristics of a medical device, inaccordance with embodiments of the present invention. Initially, at step410, a notification is provided to a mobile device. The notification isassociated with an infusion. In one embodiment, the notification is amodification to an order associated with the infusion device. In oneembodiment the notification is a suggested protocol. In one embodiment,the notification is communicated from an EMR associated with thepatient, a healthcare application, an infusion application, and thelike.

At step 412, a confirmation of the notification is received from theclinician. The confirmation is communicated to an EMR associated with apatient receiving an infusion from the infusion device. The notificationis communicated, at step 414, from the EMR to the infusion device.Characteristics of the infusion are automatically modified, at step 416,in accordance with the notification.

In one embodiment, the notification is an alarm associated with theinfusion device. The mobile device may be detected to be in proximity ofthe infusion device (e.g., in the same room, within a certain distancesuch that an alarm is audible, etc.). The alarm associated with theinfusion device may be automatically suppressed. Data associated withthe alarm may be communicated to the EMR associated with the patient.

Many different arrangements of the various components depicted, as wellas components not shown, are possible without departing from the scopeof the claims below. Embodiments of our technology have been describedwith the intent to be illustrative rather than restrictive. Alternativeembodiments will become apparent to readers of this disclosure after andbecause of reading it. Alternative means of implementing theaforementioned can be completed without departing from the scope of theclaims below. Certain features and subcombinations are of utility andmay be employed without reference to other features and subcombinationsand are contemplated within the scope of the claims.

What is claimed is:
 1. One or more computer storage media storingcomputer-useable instructions that, when used by one or more computingdevices, cause the one or more computing devices to perform operationscomprising: providing, at a mobile device associated with a clinician,data communicated by an infusion device providing an infusion to apatient; receiving a notification associated with the infusion device;communicating the notification to the mobile device; receiving aconfirmation of the notification from the clinician via the mobiledevice; communicating the notification to the infusion device; andautomatically modifying characteristics of the infusion in accordancewith the notification.
 2. The media of claim 1, wherein the notificationis a modification to an order associated with the infusion device. 3.The media of claim 1, wherein the notification is a suggested protocol.4. The media of claim 1, wherein the notification is communicated froman electronic medical record associated with the patient.
 5. The mediaof claim 1, wherein the notification is an alarm associated with theinfusion device.
 6. The media of claim 5, further comprising, detectingthat the mobile device is in proximity to the infusion device.
 7. Themedia of claim 6, further comprising automatically suppressing the alarmassociated with the infusion device.
 8. The media of claim 7, furthercomprising communicating data associated with the alarm to an electronicmedical record associated with the patient.
 9. A computer-implementedmethod in a clinical computing environment comprising: providing, via afirst computing process, a notification at a mobile device, thenotification being associated with an infusion device; receiving, via asecond computing process, a confirmation of the notification from theclinician, the confirmation being communicated to an electronic medicalrecord (EMR) associated with a patient receiving an infusion from theinfusion device; communicating, via a third computing process, thenotification from the EMR to the infusion device; and automaticallymodifying, via a fourth computing process, characteristics of theinfusion in accordance with the notification; wherein each computingprocess is performed by one or more computing devices.
 10. The method ofclaim 9, wherein the notification is a modification to an orderassociated with the infusion device.
 11. The method of claim 9, whereinthe notification is a suggested protocol.
 12. The method of claim 9,wherein the notification is communicated from an electronic medicalrecord associated with the patient.
 13. The method of claim 9, whereinthe notification is an alarm associated with the infusion device. 14.The method of claim 9, further comprising, detecting, via a fifthcomputing process, that the mobile device is in proximity to theinfusion device.
 15. The method of claim 14, further comprisingautomatically suppressing, via a sixth computing process, the alarmassociated with the infusion device.
 16. The method of claim 15, furthercomprising communicating, via a seventh computing process, dataassociated with the alarm to the EMR associated with the patient.
 17. Asystem comprising: one or more processors; and one or more computerstorage media storing instructions that, when used by the one or moreprocessors, cause the one or more processors to: provide a notificationat a mobile device, the notification being associated with an infusiondevice; receive a confirmation of the notification from the clinician,the confirmation being communicated to an electronic medical record(EMR) associated with a patient receiving an infusion from the infusiondevice; communicate the notification from the EMR to the infusiondevice; and automatically modify characteristics of the infusion inaccordance with the notification.
 18. The system of claim 17, furthercomprising the one or more computer storage media storing instructionsthat, when used by the one or more processors, cause the one or moreprocessors to detect that the mobile device is in proximity to theinfusion device.
 19. The system of claim 18, further comprising the oneor more computer storage media storing instructions that, when used bythe one or more processors, cause the one or more processors toautomatically suppress the alarm associated with the infusion device.20. The system of claim 19, further comprising the one or more computerstorage media storing instructions that, when used by the one or moreprocessors, cause the one or more processors to communicate dataassociated with the alarm to the EMR associated with the patient.